[RELEASE] integration v24.10 - #731
Merged
Merged
Conversation
Forward-merge branch-24.08 into branch-24.10
A few small tweaks to `update-version.sh` for alignment across RAPIDS. Authors: - Bradley Dice (https://github.com/bdice) Approvers: - James Lamb (https://github.com/jameslamb) URL: #717
Increase maximum UCX runtime pin to support UCX up to `v1.17.x`, but support `v1.15.0` and above until we gain confidence with newer UCX. Authors: - Peter Andreas Entschev (https://github.com/pentschev) Approvers: - Mike Sarahan (https://github.com/msarahan) - James Lamb (https://github.com/jameslamb) - Ray Douglass (https://github.com/raydouglass) URL: #712
… nightlies. (#690) This PR adds tests that run on every `integration` PR and on a nightly basis to ensure that RAPIDS conda environments can be solved with recent packages. This will help us diagnose and react to problems arising from conda environment conflicts, which sometimes force conda to select older nightly builds of RAPIDS packages. A partial solution for rapidsai/ops#2947. Next steps: - [x] Wait for rapidsai/cugraph#4639 to merge. - [x] After this PR is merged, merge rapidsai/workflows#59 as well. Authors: - Bradley Dice (https://github.com/bdice) Approvers: - James Lamb (https://github.com/jameslamb) URL: #690
Co-authored-by: Bradley Dice <bdice@bradleydice.com>
All RAPIDS libraries have been updated with Python 3.12 support, so Python 3.12 changes have been merged into `branch-24.10` of `shared-workflows`: rapidsai/shared-workflows#213 This updates GitHub Actions configs here to that branch.
Contributes to rapidsai/build-planning#56 With rapidsai/cuspatial#1441, it should be possible to revert some of the workarounds introduced in #719. ## Notes for Reviewers ### How to test this if this is working, we should see the following in the conda solves: * `fmt >=11.0.2` * `spdlog >=1.14.1` We won't see `numpy >=2` yet, because `cugraph` doesn't support it yet (rapidsai/cugraph#4615). Authors: - James Lamb (https://github.com/jameslamb) Approvers: - Bradley Dice (https://github.com/bdice) URL: #722
Contributes to rapidsai/build-planning#102 Some RAPIDS libraries are using `ncclCommSplit()`, which was introduced in `nccl==2.18.1.1`. This is part of a series of PRs across RAPIDS updating libraries' pins to `nccl>=2.18.1.1` to ensure they get a new-enough version that supports that. Authors: - James Lamb (https://github.com/jameslamb) Approvers: - Vyas Ramasubramani (https://github.com/vyasr) URL: #723
Follow-up to #723 This bumps the NCCL floor here slightly higher, to `>=2.19`. Part of a RAPIDS-wide update of that floor for the 24.10 release. See rapidsai/build-planning#102 (comment) for context. Authors: - James Lamb (https://github.com/jameslamb) Approvers: - Kyle Edwards (https://github.com/KyleFromNVIDIA) URL: #726
This PR removes the NumPy<2 pin which is expected to work for RAPIDS projects once CuPy 13.3.0 is released (CuPy 13.2.0 had some issues preventing the use with NumPy 2). Authors: - Sebastian Berg (https://github.com/seberg) - James Lamb (https://github.com/jameslamb) Approvers: - https://github.com/jakirkham URL: #718
This fixes failures in the new testing workflow from #690. **Update:** the root cause was that `rapids-conda-retry` is sending `2>&1`. The warning is being sent to stderr as intended. The old contents are partially incorrect. We can still solve this by providing `--quiet`, without needing to change `rapids-conda-retry`. <details><summary>Old issue contents</summary> Output like this is shown, even with the `--json` flag to conda: ``` ==> WARNING: A newer version of conda exists. <== current version: 24.9.0 latest version: 24.9.1 Please update conda by running $ conda update -n base -c conda-forge conda ``` The only way to make the output "proper JSON" is to pass `--quiet` as well. This seems like unintentional behavior from conda. The docs from `conda create --help` literally say: ``` --json Report all output as json. Suitable for using conda programmatically. ``` </details> Authors: - Bradley Dice (https://github.com/bdice) Approvers: - James Lamb (https://github.com/jameslamb) - Mike Sarahan (https://github.com/msarahan) URL: #729
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
❄️ Code freeze for
branch-24.10and v24.10 releaseWhat does this mean?
Only critical/hotfix level issues should be merged into
branch-24.10until release (merging of this PR).What is the purpose of this PR?
branch-24.10intomainfor the release